Conference 2014

[ Start > PikeDevel > Conference 2014 ] [ Edit this Page | Viewing Version 6 ]


Conference Topics

  • Should we identify the criteria for what features get added to given branches (devel vs stable)? Who will declare a development branch stable?
  • What are the powers of the release manager?
  • Should we have procedures for adding new features to a stable branch. Note: do we need this if our stable releases happen at reasonable intervals? Note note: Aren't feature branches the tool to deal with long development cycles of complex features?
  • consistent type for sizes? (size_t, etc)
  • pointer aliasing in pike strings. There are several possibilities to fix this "for good". For instance by having a union of char[4], short[2] and int[1] arrays at the end. Alternatively, if string data was allocated seperately from the struct pike_string, a void pointer would could be correctly casted to all 3 string types without breaking aliasing rules.
  • arm32 machine code support (tobi/arne)
  • should we have a defined procedure for deprecating an API? (arne)

Powered by PikeWiki2

 
gotpike.org | Copyright © 2004 - 2009 | Pike is a trademark of Department of Computer and Information Science, Linköping University